-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable docker layer caching in github action #4108
Conversation
The test actually ran 8 mins faster 👀 Was it the caching that was making it take so long? 😝 |
@esizer Whaaaa! Bwahaha omg ok, maybe we should just remove it completely. That's wiiiild :) |
I wonder if lack of disk space was causing tests to overrun timeouts... cursory impression is that this seems to be less failure-prone |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳 to shorter build times!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not too sure how to test this other than observe the run on this PR, but the code looks good!
Thanks @petertgiles and @mnigh! (And yeah Peter, the CI is kinda the evaluation for this stuff, I guess? In the future, I can explicitly say that in the "testing instructions" when that's the case..!) |
Spun out from: #4035 (comment) h/t @mnigh
This was causing e2e-tests to show as "skipped", and rarely showing the proper pass/fail status, which makes the e2e tests pretty useless.
Disabling docker layer cache for now, to avoid the github action "out of storage" error. We'll see in the github action run whether it makes the workflow run significantly longer (20-25 min seems to be regular).